Update EIP-7928: change BAL retention period to WSP#10940
Update EIP-7928: change BAL retention period to WSP#10940eth-bot merged 2 commits intoethereum:masterfrom
Conversation
|
✅ All reviewers have approved. |
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
Head branch was pushed to by a user without write access
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
trizist
left a comment
There was a problem hiding this comment.
This proposal is a strong and well-motivated step toward scalable execution-layer performance. Block-Level Access Lists strike a pragmatic balance between full witnesses and transaction-level access lists by providing deterministic, post-execution state information with manageable overhead. The ability to enable parallel disk reads, parallel transaction execution, executionless state updates, and faster state root computation makes BALs particularly compelling as Ethereum moves toward multi-core clients and more execution-light validation models.
The recent change to retain BALs for the weak subjectivity period is especially important, as it aligns BAL availability with Ethereum’s security assumptions and improves robustness for long-offline nodes. While client complexity and storage considerations are real trade-offs, the measured size overhead appears reasonable given the substantial gains in sync performance, validation efficiency, and future compatibility with Verkle trees and statelessness research. Overall, this EIP meaningfully advances Ethereum’s long-term execution roadmap without altering EVM semantics.
As based on the discussion here, EL may store enough BAL to enable nodes that were offline for less than the WSP to catch up doing re-execution (for which BALs are needed):
https://discord.com/channels/595666850260713488/1364000387195076608/1450572627700617268